CherryPicked: [cnv-4.18] Remove Artifactory dependency from CPU affinity by OhadRevah · Pull Request #3324 · RedHatQE/openshift-virtualization-tests

OhadRevah · 2026-01-05T12:41:39Z

The test for kubevirt_vmi_node_cpu_affinity is flaky duo to connectivity issues with the artifactory, in this PR I modified the test to not rely on the artifactory to avoid this kind of failures to stabilize the observability lanes.

https://issues.redhat.com/browse/CNV-75209
original PR:#3134

Short description:

More details:

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for reviewer:

jira-ticket:

https://issues.redhat.com/browse/CNV-75854

…ity test The test for kubevirt_vmi_node_cpu_affinity is flaky duo to connectivity issues with the artifactory, in this PR I modified the test to not rely on the artifactory to avoid this kind of failures to stabilize the observability lanes. https://issues.redhat.com/browse/CNV-75209

coderabbitai · 2026-01-05T12:41:44Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

openshift-virtualization-qe-bot-5 · 2026-01-05T12:42:09Z

Report bugs in Issues

Welcome! 🎉

This pull request will be automatically processed with the following features:

🔄 Automatic Actions

Reviewer Assignment: Reviewers are automatically assigned based on the OWNERS file in the repository root
Size Labeling: PR size labels (XS, S, M, L, XL, XXL) are automatically applied based on changes
Issue Creation: A tracking issue is created for this PR and will be closed when the PR is merged or closed
Pre-commit Checks: pre-commit runs automatically if .pre-commit-config.yaml exists
Branch Labeling: Branch-specific labels are applied to track the target branch
Auto-verification: Auto-verified users have their PRs automatically marked as verified

📋 Available Commands

PR Status Management

/wip - Mark PR as work in progress (adds WIP: prefix to title)
/wip cancel - Remove work in progress status
/hold - Block PR merging (approvers only)
/hold cancel - Unblock PR merging
/verified - Mark PR as verified
/verified cancel - Remove verification status
/reprocess - Trigger complete PR workflow reprocessing (useful if webhook failed or configuration changed)

Review & Approval

/lgtm - Approve changes (looks good to me)
/approve - Approve PR (approvers only)
/automerge - Enable automatic merging when all requirements are met (maintainers and approvers only)
/assign-reviewers - Assign reviewers based on OWNERS file
/assign-reviewer @username - Assign specific reviewer
/check-can-merge - Check if PR meets merge requirements

Testing & Validation

/retest tox - Run Python test suite with tox
/retest build-container - Rebuild and test container image
/retest all - Run all available tests

Container Operations

/build-and-push-container - Build and push container image (tagged with PR number)
- Supports additional build arguments: /build-and-push-container --build-arg KEY=value

Cherry-pick Operations

/cherry-pick <branch> - Schedule cherry-pick to target branch when PR is merged
- Multiple branches: /cherry-pick branch1 branch2 branch3

Label Management

/<label-name> - Add a label to the PR
/<label-name> cancel - Remove a label from the PR

✅ Merge Requirements

This PR will be automatically approved when the following conditions are met:

Approval: /approve from at least one approver
LGTM Count: Minimum 2 /lgtm from reviewers
Status Checks: All required status checks must pass
No Blockers: No WIP, hold, or conflict labels
Verified: PR must be marked as verified (if verification is enabled)

📊 Review Process

Approvers and Reviewers

Approvers:

dshchedr
myakove
rnetser
vsibirsk

Reviewers:

OhadRevah
RoniKishner
dshchedr
hmeir
rnetser
vsibirsk

Available Labels

hold
verified
wip
lgtm
approve
automerge

💡 Tips

WIP Status: Use /wip when your PR is not ready for review
Verification: The verified label is automatically removed on each new commit
Cherry-picking: Cherry-pick labels are processed when the PR is merged
Container Builds: Container images are automatically tagged with the PR number
Permission Levels: Some commands require approver permissions
Auto-verified Users: Certain users have automatic verification and merge privileges

For more information, please refer to the project documentation or contact the maintainers.

OhadRevah · 2026-01-05T12:49:46Z

/build-and-push-container

openshift-virtualization-qe-bot-2 · 2026-01-05T12:54:47Z

New container for quay.io/openshift-cnv/openshift-virtualization-tests:pr-3324 published

OhadRevah · 2026-01-05T15:09:09Z

/verified

Running the test, build 4038

openshift-virtualization-qe-bot-3 · 2026-01-05T15:09:50Z

@coderabbitai

Test execution plan request details

CRITICAL: You MUST post an inline review comment on the first changed line of the first file.
The inline comment should contain the Test Execution Plan with the smoke tests recommendation.
Do NOT submit a formal review - just post the inline comment directly.

As an expert software testing engineer, analyze all modified files in this PR and create a targeted test execution plan.
You will post an inline review comment with the test execution plan on the first changed file.
If you fail to run or post a comment, retry.

Analysis Requirements:

Examine code changes in each modified file
Identify affected code paths, functions, and classes
Analyze pytest-specific elements: fixtures (scope, dependencies), parametrization, markers, conftest changes
Trace test dependencies through imports, shared utilities, and fixture inheritance
Detect new tests introduced in the PR
Smoke Test Impact Analysis: Determine if any changes could affect smoke tests by checking:
- Changes to files/functions used by tests marked with @pytest.mark.smoke
- Changes to fixtures or utilities imported by smoke tests
- Changes to conftest.py files that may affect smoke test execution
- Changes to core infrastructure code (utilities/, libs/) that smoke tests depend on

Your deliverable:
Your change request comment will be based on the following requirements:

Test Execution Plan

Run smoke tests: True / False (Based on your smoke test impact analysis - True if any changes may affect smoke tests)
path/to/test_file.py - When the entire test file needs verification
path/to/test_file.py::TestClass::test_method - When specific test(s) needed
path/to/test_file.py::test_function - When specific test(s) needed
-m marker - When specific marker(s) can be used to cover multiple cases.

Guidelines:

Include only tests directly affected by the changes
Use a full file path only if ALL tests in that file require verification
Use file path + test name if only specific tests are needed
If a test marker can cover multiple files/tests, provide the marker
Balance coverage vs over-testing - Keep descriptions minimal

CRITICAL WORKFLOW COMPLETION RULES:

When responding to this test execution plan request, you MUST follow these rules EXACTLY:

YOUR ONLY DELIVERABLE: Post an inline review comment containing the test execution plan on the first changed line
THEN STOP IMMEDIATELY - Do NOT generate any additional response
FALLBACK ONLY: If submitting the review fails after retrying, post as a regular PR comment
SILENCE = SUCCESS: After successfully submitting the review, your task is complete. No confirmation needed.

ABSOLUTE PROHIBITIONS (violating these creates empty/meaningless reviews):

❌ Do NOT post acknowledgment messages like "Test execution plan posted", "Review posted successfully", "I've successfully posted"
❌ Do NOT mention review IDs, URLs, or confirmation of posting in the PR thread
❌ Do NOT add any follow-up comments after submitting the review
❌ Do NOT reply to confirm task completion
❌ Do NOT explain what you did - just do it and stop

Remember: The pull request review is visible to users. Additional comments are redundant noise.

CRITICAL: Before setting "Run smoke tests: True", you MUST use shell scripts to:
- Trace the actual fixture dependency chain from smoke tests to changed fixtures
- Verify that smoke tests actually import/use changed utilities or functions
- Confirm the dependency path exists; do NOT assume based on scope or semantics
- Be conservative: Session-scoped fixtures or infrastructure-sounding names do NOT
automatically mean smoke test impact. Only flag smoke test impact when you can
demonstrate a concrete dependency path.
WRONG: "This session-scoped storage fixture might affect smoke tests"
RIGHT: "Smoke test X uses fixture Y, which depends on the changed fixture Z"

coderabbitai · 2026-01-05T15:11:40Z

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Get PR details and changed files
gh pr view 3324 --json files --jq '.files[] | "\(.path) +\(.additions) -\(.deletions)"'

Length of output: 196

🏁 Script executed:

#!/bin/bash
# Get the diff to see what changed
gh pr diff 3324

Length of output: 6676

🏁 Script executed:

#!/bin/bash
# Find all smoke tests in the repository
rg "pytest\.mark\.smoke" --type=py -B2 | grep "def test_" | head -20

Length of output: 0

🏁 Script executed:

#!/bin/bash
# Try alternative search for smoke tests
rg "@pytest\.mark\.smoke|pytest\.mark\.smoke" --type=py -C1 | head -40

Length of output: 2734

🏁 Script executed:

#!/bin/bash
# Check if any smoke tests import or use observability metrics
rg "from tests\.observability" --type=py -g "*test*.py" | head -20

Length of output: 2246

🏁 Script executed:

#!/bin/bash
# Check if vm_with_cpu_spec fixture is used anywhere else
rg "vm_with_cpu_spec" --type=py -C2

Length of output: 4243

🏁 Script executed:

#!/bin/bash
# Check if any smoke tests use prometheus fixture or metrics validation
rg "pytest\.mark\.smoke" --type=py -A10 | rg -i "prometheus|metrics|observability" -C2

Length of output: 0

🏁 Script executed:

#!/bin/bash
# Get the first file and first line that was changed for posting the inline comment
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/3324/files --jq '.[0] | {filename: .filename, patch: .patch}'

Length of output: 974

🏁 Script executed:

#!/bin/bash
# Get the latest commit SHA for the PR to post inline comment
gh pr view 3324 --json commits --jq '.commits[-1].oid'

Length of output: 40

🏁 Script executed:

#!/bin/bash
# Verify no smoke tests depend on observability/metrics by checking imports
rg "pytest\.mark\.smoke" --type=py -l | xargs -I {} rg "from tests\.observability|import.*observability" {} 2>/dev/null || echo "No observability imports in smoke tests"

Length of output: 39

🏁 Script executed:

#!/bin/bash
# Post inline review comment with test execution plan on the first changed line
gh api \
  --method POST \
  -H "Accept: application/vnd.github+json" \
  /repos/RedHatQE/openshift-virtualization-tests/pulls/3324/reviews \
  -f event='COMMENT' \
  -f comments[][path]='tests/observability/metrics/conftest.py' \
  -f comments[][line]=399 \
  -f comments[][side]='RIGHT' \
  -f comments[][body]='## Test Execution Plan

**Run smoke tests: False**

The changes are isolated to the observability/metrics module and do not affect smoke tests. Verified that no smoke tests import or depend on the observability module.

### Tests to Execute:

- `tests/observability/metrics/test_general_metrics.py::TestVmiNodeCpuAffinity::test_kubevirt_vmi_node_cpu_affinity` - Modified test that now uses new fixture-based approach instead of Artifactory-dependent RHEL template
- `tests/observability/metrics/test_vms_metrics.py::TestVmResourceRequests` - Uses the same `vm_with_cpu_spec` fixture, verify no regression

### Rationale:

This PR removes the Artifactory dependency by:
1. Adding `expected_cpu_affinity_metric_value` fixture to calculate expected metric values directly
2. Replacing RHEL template-based VM creation with existing `vm_with_cpu_spec` fixture
3. Removing now-unused utility functions `get_vm_cpu_info_from_prometheus` and `validate_vmi_node_cpu_affinity_with_prometheus`

The modified test and any other tests using the `vm_with_cpu_spec` fixture should be verified to ensure the refactoring maintains functionality.' \
  -f commit_id='16f23452b8e4959dbf389fb7da40c61a5525385a'

Length of output: 274

🏁 Script executed:

#!/bin/bash
# Post inline review comment with test execution plan - using -F for integer line number
gh api \
  --method POST \
  -H "Accept: application/vnd.github+json" \
  /repos/RedHatQE/openshift-virtualization-tests/pulls/3324/reviews \
  -f event='COMMENT' \
  -f comments[][path]='tests/observability/metrics/conftest.py' \
  -F comments[][line]=399 \
  -f comments[][side]='RIGHT' \
  -f comments[][body]='## Test Execution Plan

**Run smoke tests: False**

The changes are isolated to the observability/metrics module and do not affect smoke tests. Verified that no smoke tests import or depend on the observability module.

### Tests to Execute:

- `tests/observability/metrics/test_general_metrics.py::TestVmiNodeCpuAffinity::test_kubevirt_vmi_node_cpu_affinity` - Modified test that now uses new fixture-based approach instead of Artifactory-dependent RHEL template
- `tests/observability/metrics/test_vms_metrics.py::TestVmResourceRequests` - Uses the same `vm_with_cpu_spec` fixture, verify no regression

### Rationale:

This PR removes the Artifactory dependency by:
1. Adding `expected_cpu_affinity_metric_value` fixture to calculate expected metric values directly
2. Replacing RHEL template-based VM creation with existing `vm_with_cpu_spec` fixture
3. Removing now-unused utility functions `get_vm_cpu_info_from_prometheus` and `validate_vmi_node_cpu_affinity_with_prometheus`

The modified test and any other tests using the `vm_with_cpu_spec` fixture should be verified to ensure the refactoring maintains functionality.' \
  -f commit_id='16f23452b8e4959dbf389fb7da40c61a5525385a'

Length of output: 1728

🧠 Learnings used

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-12-16T14:00:59.076Z
Learning: In the openshift-virtualization-tests repository, when responding to test execution plan requests from openshift-virtualization-qe-bot-3, CodeRabbit must post ONLY an inline review comment on the Files Changed tab and then stop immediately without generating any follow-up comments in the PR discussion thread. No acknowledgment messages, no confirmation of posting, no explanation - silence after posting the inline review equals success. Additional comments create empty/meaningless reviews that clutter the PR.

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-12-16T10:28:54.212Z
Learning: In the openshift-virtualization-tests repository, when determining smoke test impact for test execution plans, only set "Run smoke tests: True" if there is a verified, traceable dependency path from smoke tests to the changed code. Session-scoped fixtures or infrastructure-sounding changes do NOT automatically imply smoke test impact - the dependency chain must be explicitly verified using shell scripts before recommending smoke test execution.

Learnt from: jpeimer
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-12-22T15:56:00.157Z
Learning: In the openshift-virtualization-tests repository, when responding to test execution plan requests from openshift-virtualization-qe-bot-3, do NOT use "REQUEST_CHANGES" review type if the PR author has already marked the PR as verified (e.g., with `/verified` command). Test execution plans are informational guides, not blocking requirements. Use COMMENT event for informational test plans, or only REQUEST_CHANGES if there are actual code issues that need to be addressed before merging.

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 2469
File: utilities/sanity.py:139-142
Timestamp: 2025-11-08T07:36:57.616Z
Learning: In the openshift-virtualization-tests repository, user rnetser prefers to keep refactoring PRs (like PR #2469) strictly focused on moving/organizing code into more granular modules without adding new functionality, error handling, or behavioral changes. Such improvements should be handled in separate PRs.

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 3062
File: conftest.py:333-333
Timestamp: 2025-12-16T20:11:03.645Z
Learning: In the openshift-virtualization-tests repository, when determining smoke test impact for changes affecting py_config["os_login_param"], follow this verification methodology: (1) Find all smoke tests: `rg "pytest.mark.smoke" --type=py -B2 | grep "def test_"`, (2) For each smoke test file, search for VM creation patterns: `rg "VirtualMachineForTests|running_vm|VirtualMachineForTestsFromTemplate|wait_for_ssh|check_ssh_connectivity"`, (3) Trace the dependency chain: smoke test → VirtualMachineForTests/running_vm() → wait_for_ssh_connectivity() (default enabled) → vm.login_params property → py_config["os_login_param"][vm.os_flavor], (4) Check utilities/virt.py for login_params usage: `rg "os_login_param|login_params" utilities/virt.py -C3`. Any smoke test creating VMs with default SSH connectivity checks (running_vm with check_ssh_connectivity=True) depends on os_login_param, even if the test doesn't directly reference it.

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 3228
File: .coderabbit.yaml:30-41
Timestamp: 2026-01-05T10:33:50.728Z
Learning: In the openshift-virtualization-tests repository, user rnetser prefers minimal pre-merge checks in CodeRabbit configuration: only docstrings enforcement (80% threshold) is needed, not title or description checks.

Learnt from: vamsikrishna-siddu
Repo: RedHatQE/openshift-virtualization-tests PR: 2199
File: tests/storage/test_online_resize.py:108-113
Timestamp: 2025-09-28T14:43:07.181Z
Learning: In the openshift-virtualization-tests repo, PR #2199 depends on PR #2139 which adds architecture-specific OS_FLAVOR attributes to the Images.Cirros class (OS_FLAVOR_CIRROS for x86_64/ARM64, OS_FLAVOR_FEDORA for s390x), enabling conditional logic based on the underlying OS flavor in tests.

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-12-16T14:06:22.391Z
Learning: In the openshift-virtualization-tests repository, when posting test execution plan inline review comments using GitHub API, the full test execution plan content must go in the `comments[].body` field (which appears on Files Changed tab), NOT in the top-level `body` field (which appears in PR discussion thread). The top-level `body` field should be omitted or left empty to avoid posting redundant comments in the PR discussion thread.

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 3062
File: conftest.py:333-333
Timestamp: 2025-12-16T15:09:49.597Z
Learning: In the openshift-virtualization-tests repository, when conftest.py or utilities/bitwarden.py changes affect py_config["os_login_param"], smoke test impact must be determined by: (1) finding all smoke tests using `rg "pytest.mark.smoke"`, (2) checking each for VM creation patterns (VirtualMachineForTests, running_vm, VirtualMachineForTestsFromTemplate), (3) tracing whether running_vm is called with default check_ssh_connectivity=True, which accesses vm.login_params property that reads py_config["os_login_param"][vm.os_flavor]. The dependency chain is: smoke test → VM creation → running_vm → wait_for_ssh_connectivity → vm.login_params → os_login_param. Any smoke test creating VMs with SSH connectivity (the default) depends on os_login_param.

Learnt from: vamsikrishna-siddu
Repo: RedHatQE/openshift-virtualization-tests PR: 2199
File: tests/storage/test_online_resize.py:108-113
Timestamp: 2025-09-28T14:43:07.181Z
Learning: In the openshift-virtualization-tests repo, PR #2199 depends on PR #2139 which adds the OS_FLAVOR attribute to the Images.Cirros class, making Images.Cirros.OS_FLAVOR available for conditional logic in tests.

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-09-29T19:05:24.987Z
Learning: The test execution plan for PR #1904 focuses on cluster-type conditional logic where nmstate functionality is bypassed on cloud clusters (Azure/AWS) but fully functional on bare-metal/PSI clusters, requiring different test strategies for each environment type.

Learnt from: yossisegev
Repo: RedHatQE/openshift-virtualization-tests PR: 3196
File: tests/network/upgrade/test_upgrade_network.py:4-4
Timestamp: 2025-12-22T16:27:44.327Z
Learning: For PRs that remove test cases (especially redundant test cleanup PRs in openshift-virtualization-tests), test collection verification (pytest --collect-only showing selected/deselected counts) is sufficient to confirm the removal was clean and the test module remains functional. Full test execution is not required for test deletion PRs.

Learnt from: servolkov
Repo: RedHatQE/openshift-virtualization-tests PR: 1776
File: libs/net/node_network.py:25-31
Timestamp: 2025-08-20T23:43:28.117Z
Learning: In the RedHatQE/openshift-virtualization-tests project, servolkov's team always uses bare metal (BM) clusters with IPv4 setup in their testing environment, making defensive checks for IPv4 data presence potentially redundant in their networking code.

Learnt from: jpeimer
Repo: RedHatQE/openshift-virtualization-tests PR: 1160
File: tests/storage/storage_migration/test_mtc_storage_class_migration.py:165-176
Timestamp: 2025-06-17T07:45:37.776Z
Learning: In the openshift-virtualization-tests repository, user jpeimer prefers explicit fixture parameters over composite fixtures in test methods, even when there are many parameters, as they find this approach more readable and maintainable for understanding test dependencies.

Learnt from: akri3i
Repo: RedHatQE/openshift-virtualization-tests PR: 1210
File: tests/virt/cluster/general/mass_machine_type_transition_tests/conftest.py:24-64
Timestamp: 2025-06-23T19:28:20.281Z
Learning: In OpenShift Virtualization mass machine type transition tests, the machine type glob pattern "pc-q35-rhel8.*.*" is intentionally hard-coded in the kubevirt_api_lifecycle_automation_job as it's used only once for this specific test case, with plans to update it in the future if the job needs to support other machine types.

Learnt from: RoniKishner
Repo: RedHatQE/openshift-virtualization-tests PR: 1411
File: utilities/os_utils.py:246-279
Timestamp: 2025-07-22T17:13:59.166Z
Learning: In the RedHatQE/openshift-virtualization-tests repository, CentOS preferences follow the format "centos-stream<version>" (e.g., "centos-stream9", "centos-stream10"). The generate_instance_type_centos_os_matrix function correctly uses regex to extract numeric versions and constructs the latest version string in the same format as the input preferences for proper comparison.

Learnt from: akri3i
Repo: RedHatQE/openshift-virtualization-tests PR: 1210
File: tests/virt/cluster/general/mass_machine_type_transition_tests/conftest.py:83-97
Timestamp: 2025-06-23T19:19:31.961Z
Learning: In OpenShift Virtualization mass machine type transition tests, the kubevirt_api_lifecycle_automation_job requires cluster-admin privileges to function properly, as confirmed by the test maintainer akri3i.

Learnt from: yossisegev
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-12-07T14:51:53.484Z
Learning: In the openshift-virtualization-tests repository, the team has decided to avoid using predefined time constants (like TIMEOUT_2MIN, TIMEOUT_5SEC) and prefers using explicit numeric values for timeout parameters.

Learnt from: dshchedr
Repo: RedHatQE/openshift-virtualization-tests PR: 1716
File: tests/virt/conftest.py:289-297
Timestamp: 2025-08-09T01:52:26.683Z
Learning: When user dshchedr moves working code from one location to another in the openshift-virtualization-tests repository, they prefer not to modify it unless there's a real issue, maintaining the original implementation to avoid introducing unnecessary changes.

Learnt from: vsibirsk
Repo: RedHatQE/openshift-virtualization-tests PR: 2045
File: tests/virt/cluster/vm_lifecycle/conftest.py:46-47
Timestamp: 2025-09-15T06:49:53.478Z
Learning: In the openshift-virtualization-tests repo, large fixture refactoring efforts like the golden image data source migration are handled incrementally by directory/team ownership. The virt/cluster directory is handled separately from virt/node, tests/infra, tests/storage, etc., with each area managed by relevant teams in follow-up PRs.

Learnt from: dshchedr
Repo: RedHatQE/openshift-virtualization-tests PR: 1932
File: tests/virt/node/migration_and_maintenance/conftest.py:65-72
Timestamp: 2025-09-29T20:33:51.007Z
Learning: In tests/virt/node/migration_and_maintenance/conftest.py, the added_vm_cpu_limit fixture doesn't require ResourceEditor as a context manager because it's the final test to modify the vm_for_multifd_test VM before teardown, so restoration of CPU limits is unnecessary overhead as confirmed by maintainer dshchedr.

Learnt from: chandramerla
Repo: RedHatQE/openshift-virtualization-tests PR: 2577
File: tests/virt/node/workload_density/test_free_page_reporting.py:90-90
Timestamp: 2025-11-20T16:27:01.693Z
Learning: The virtio_balloon free page reporting issue on s390x architecture (tracked in OCPBUGS-51113) has been fixed. Free page reporting tests in tests/virt/node/workload_density/test_free_page_reporting.py are now safe to run on s390x clusters.

Learnt from: akri3i
Repo: RedHatQE/openshift-virtualization-tests PR: 1210
File: tests/virt/cluster/general/mass_machine_type_transition_tests/conftest.py:142-149
Timestamp: 2025-06-23T19:18:12.275Z
Learning: In OpenShift Virtualization machine type transition tests, the kubevirt_api_lifecycle_automation_job updates VM machine types to the latest version based on a MACHINE_TYPE_GLOB pattern, and subsequent fixtures may intentionally revert the machine type to test bidirectional transition behavior.

rnetser

please add the orig PR in the description

OhadRevah · 2026-01-06T15:07:43Z

please add the orig PR in the description

Done

rnetser · 2026-01-07T17:33:54Z

/approve
/lgtm

openshift-virtualization-qe-bot-5 · 2026-01-11T11:47:57Z

Successfully removed PR tag: quay.io/openshift-cnv/openshift-virtualization-tests:pr-3324.

openshift-virtualization-qe-bot-5 · 2026-01-11T11:51:21Z

New container for quay.io/openshift-cnv/openshift-virtualization-tests:cnv-4.18 published

github-actions Bot added the sig-iuo label Jan 5, 2026

openshift-virtualization-qe-bot-5 requested a review from hmeir January 5, 2026 12:42

openshift-virtualization-qe-bot-5 assigned OhadRevah Jan 5, 2026

openshift-virtualization-qe-bot-5 mentioned this pull request Jan 5, 2026

CherryPicked: [cnv-4.18] Remove Artifactory dependency from CPU affinity - 3324 #3325

Closed

openshift-virtualization-qe-bot-5 requested a review from RoniKishner January 5, 2026 12:42

openshift-virtualization-qe-bot-5 added branch-cnv-4.18 size/M labels Jan 5, 2026

openshift-virtualization-qe-bot-5 requested review from dshchedr, rnetser and vsibirsk January 5, 2026 12:42

openshift-virtualization-qe-bot approved these changes Jan 5, 2026

View reviewed changes

openshift-virtualization-qe-bot-3 added the lgtm-openshift-virtualization-qe-bot label Jan 5, 2026

openshift-virtualization-qe-bot-3 added the verified label Jan 5, 2026

coderabbitai Bot reviewed Jan 5, 2026

View reviewed changes

Comment thread tests/observability/metrics/conftest.py

openshift-virtualization-qe-bot-4 added the commented-coderabbitai[bot] label Jan 5, 2026

rnetser requested changes Jan 6, 2026

View reviewed changes

openshift-virtualization-qe-bot-4 added the changes-requested-rnetser label Jan 6, 2026

hmeir approved these changes Jan 7, 2026

View reviewed changes

openshift-virtualization-qe-bot-5 added the lgtm-hmeir label Jan 7, 2026

dshchedr approved these changes Jan 7, 2026

View reviewed changes

openshift-virtualization-qe-bot added the lgtm-dshchedr label Jan 7, 2026

rnetser approved these changes Jan 7, 2026

View reviewed changes

openshift-virtualization-qe-bot-2 added approved-rnetser lgtm-rnetser and removed changes-requested-rnetser labels Jan 7, 2026

openshift-virtualization-qe-bot-5 added can-be-merged labels Jan 7, 2026

vsibirsk merged commit 7c9960c into RedHatQE:cnv-4.18 Jan 11, 2026
28 checks passed

OhadRevah deleted the fixCpuAffinityTest-cnv-4.18 branch January 11, 2026 11:52

Conversation

OhadRevah commented Jan 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Short description:

More details:

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for reviewer:

jira-ticket:

Uh oh!

coderabbitai Bot commented Jan 5, 2026

Review skipped

Uh oh!

openshift-virtualization-qe-bot-5 commented Jan 5, 2026

Welcome! 🎉

🔄 Automatic Actions

📋 Available Commands

PR Status Management

Review & Approval

Testing & Validation

Container Operations

Cherry-pick Operations

Label Management

✅ Merge Requirements

📊 Review Process

💡 Tips

Uh oh!

OhadRevah commented Jan 5, 2026

Uh oh!

openshift-virtualization-qe-bot-2 commented Jan 5, 2026

Uh oh!

OhadRevah commented Jan 5, 2026

Uh oh!

openshift-virtualization-qe-bot-3 commented Jan 5, 2026

Uh oh!

Uh oh!

coderabbitai Bot commented Jan 5, 2026

Uh oh!

rnetser left a comment

Choose a reason for hiding this comment

Uh oh!

OhadRevah commented Jan 6, 2026

Uh oh!

rnetser commented Jan 7, 2026

Uh oh!

Uh oh!

openshift-virtualization-qe-bot-5 commented Jan 11, 2026

Uh oh!

openshift-virtualization-qe-bot-5 commented Jan 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

10 participants

OhadRevah commented Jan 5, 2026 •

edited

Loading